User-customized call filtering system and method

ABSTRACT

A user-customized call filtering system and method for vetting and filtering incoming calls from unwanted callers including robocallers. The system and method includes a user-customized call filter software application hosted on a cloud-based system that communicates with a native call filter application stored on end-user devices including smart phones, over a wired or wireless communication network. The native call filter application includes a host of pages that are selected by and presented to, end-users to customize a blacklist and whitelist with telephone numbers associated with incoming calls that are unwanted and terminated, granted immediate access to end-users, or granted access to end-users based on predefined schedule filters that are defined by geographic location of originating callers, geographic location of end-users, and/or on a particular date, day, and/or time. The system and method includes a dynamic query engine that generates and presents queries to callers associated with unknown and unverified incoming calls to solicit human responses for determining whether such callers are human or likely robocallers.

CROSS-REFERENCE TO RELATED APPLICATION

This application claims the benefit of U.S. Provisional PatentApplication Ser. No. 62/813,514, filed Mar. 4, 2019, and ProvisionalPatent Application Ser. No. 62/968,315 filed Jan. 31, 2020 which areincorporated herein in their entireties.

FIELD OF THE INVENTION

The present invention relates generally to telephonic communicationsystems, and more particularly, to a user-customized call filteringsystem and method for selectively vetting unwanted calls from individualcallers including robocallers based on user-customized settings based ongeographic location of end-users, date and time schedules, and responsesto questions or directives generated by a dynamic query engine.

BACKGROUND OF THE INVENTION

Unwanted calls including robocalls have become a prevailing concern withthe public at large. Receiving calls from unknown callers is often timesannoying, disturbing, and most often unnecessarily interrupts dailyliving activities of called recipients. Calls associated with robocallstypically comprise machine-operated dialers that are preprogrammed tomake numerous, anonymous calls to individual households including forexample to promote telemarketing products or services, solicitparticipation in surveys, or gauge political stance in various electionsor polls. Although such auto-dialing process are often targeted torecipients of particular race, age, and/or location, most calls do notdifferentiate age when calling individuals and often reach older, morefragile individuals that are vulnerable and fall prey to deceptivecalling and sales practices. Advancements in mobile communicationtechnology has enticed robocalling entities to expand their calling basebeyond use of landline phones, to calling users or owners of mobile,electronic communication devices such as mobile or smart phones. Mobilephones are widely employed throughout the world to provide individualswith immediate accessibility to emails and texts, browse the internet,engage in social media, or simply to call friends and family. Mobilephones have given users the advantage of staying connected, at alltimes, with family and friends, and in immediate reach of receivingcalls. With the advent of both wired and wireless communication, agreater number of individuals are now receiving a host of unwanted callsincluding robocalls.

In an effort to curb receiving annoying or unwanted calls includingrobocalls, individuals have often relied on caller ID services ordevices that are engineering to help filter unwanted incoming calls. Inpractice, called recipients typically view incoming call numbers,associated with calling devices, to ascertain whether the incoming callnumber is one that is associated with a caller they recognize. Suchfiltering devices have provided limited resolve in the past because inpractice many individuals do not have or subscribe to caller ID service,are inundated with too many incoming calls, or have difficultyassociating or managing known from unknown call numbers. Calledrecipients often find themselves in a position of answering the incomingcalls as a result of possibly missing an important call that may berelated to a family emergency, or other important call. In addition,called recipients are not able to decipher whether incoming calls aremade by actual humans or by automated machine robots.

A host of call blocking devices, and software applications have alsobeen developed to better assist called recipients with unwanted calls.For example, some call blocking devices include electronic deviceshaving a processor, memory, and a database that stores preprogrammedphone numbers associated with verified callers that are known by calledrecipients. Such devices often compare the incoming phone numbers with alist of allowed phone numbers that are stored in the database to grantaccess to called recipients. Though such electronic devices arecompatible for use with landline phones, the call blocking devices aregenerally impractical for use with mobile or smart phones. To blockunwanted incoming calls directed to mobile phones, companies havedeveloped various call blocking software application programs that aremade available for called recipients using mobile phones. Such callblocking software applications generally work on similar principles ascall blocking devices that are used with landlines, in that phonenumbers associated with incoming calls are compared to a list ofpre-stored phone numbers that are deemed verified and acceptable bycalled recipients.

It is well known that robocallers use deceptive calling practices in aneffort to overcome restrictions provided by call blocking devices and/orcall blocking software applications. For instance, one techniqueinvolves using a greater number of calling numbers that are used toovercome pre-stored blocking list of numbers, and prevent calledrecipients from being familiarized with incoming call numbers. As such,a person may receive a robocall associated with one telephone number,and shortly thereafter, receive the same robocall that is associatedwith a different telephone number. Using different telephone numbers tocall individuals makes it difficult, if not impossible, for end users tokeep track of incoming numbers when preprogramming call blockingdevices, or software application used on mobile phones. Anotherdeceptive practice employed by robocallers involves spoofing a telephonenumber of a person or company living in the same geographical area ascall recipients to effectively camouflage the identity of robocallers,and pretend that the calling party is a person, or company that callrecipients recognize as being legitimate local callers. Calledrecipients viewing the incoming call recognizes the incoming telephonenumber as being associated with a known local resident, or partyassociated with a local business or entity, believing that a legitimateattempt in calling the called recipient is being made thereby enticingcalled recipients to pick up the phone. As such, previous strategies forrobocallers relying on using multiple telephone numbers is now beingreplaced with the practice of spoofing calls to deceive recipientcallers in actually believing calls are being made from a local,legitimate callers. Spoofing has gained momentum over the years, and hasbecome another arsenal used by robocallers in luring individuals toanswer the phone. Spoofing calls makes it extremely difficult for calledrecipients to add spoofed numbers to blocking lists as such numbers aretypically associated with well-known, verified callers and doing sowould effectively wanted communication between trustworthy callingparties.

Still another drawback of call filtering or blocking prior art devicesor systems is the inability or ineffectiveness to ascertain whether thecalling party is human or machine, and to restrict incoming calls basedon the location of a caller. Most prior art directed at call filteringor blocking uses various algorithms based on time cycles, audible tones,back ground noise, or call cycles to determine whether calls are madefrom humans or machines. Such techniques require sophisticatedprogramming, are unreliable, and often inaccurate. No mechanism isprovided to engage the caller to better ascertain whether the callingparty is human or not. Also, most prior art associated with callfiltering or blocking considers only call numbers associated withcallers when determining unwanted calls and does not take intoconsideration the location from which the call is being placed. Unwantedcalls may originate from other cities, or countries. As such, callrecipients are not able to filter or block incoming calls based onuser-customized caller location settings.

Accordingly, there is an established need for a solution to at least oneof the aforementioned problems. There remains a need for auser-customized call filtering system and method to easily, and quicklyselectively block or filter unwanted calls and/or text messages fromunwanted callers including robocallers based on user-customized settingsincluding geographic location of callers, end-users, and/or date, dayand time, and a blacklist, and that effectively determines whetherincoming calls are human generated calls by using a dynamic query enginethat generates and presents queries to callers to solicit and determinehuman responses versus robocallers.

SUMMARY OF THE INVENTION

The present invention is directed to a user-customized call filteringsystem and method for selectively filtering and blocking unwanted callsfrom unverified callers including robocallers based on user-customizedsettings including user customized blacklist, a whitelist with selectivescheduled filters including a geographic location filter, and/or date,day and time filter, and includes a dynamic query engine that generatesand presents queries to callers associated within incoming calls tosolicit live human responses to determine whether callers arerobocallers. The user-customized call filtering system and methodcomprises a cloud-based system hosting a user-customized call filteringsoftware platform stored in a computer-readable memory and executed byone or more processors, where the cloud-based system receives requests,comprising signals associated with telephone numbers corresponding toone or more calling devices, over a communication network, tocommunicate with end-user devices. The user-customized call filteringsystem communicates with a native call filter application downloadedonto end-user devices to filter or block telephone numbers prestored ina blacklist and a whitelist that includes schedule filters. A dynamicquery engine generates and presents queries to callers associated withincoming calls to solicit human responses. The native call filterapplication allows users to customize the blacklist with telephonenumbers generated by a contact, call log, message log, and incoming callfunctionality. The native call filter application permits users tofilter text messages when selecting SMS messaging, via a text-blockingfeature.

Introducing a first embodiment of the invention that provides auser-customized method of filtering calls, said method comprising:hosting a user-customized call filter application platform on acloud-based system where the call filter application software is storedin a computer-readable memory and executed by one or more processors onone or more servers communicating with databases, where the cloud systemreceives incoming call requests, generated by calling devices over acommunication network, to communicate with end-user devices including acall filter native application, where the incoming call requests isassociated with telephone numbers generated by the calling devices,end-users customizing the call filter native application to create calllists including prestored telephone numbers that are compared toincoming call requests to filter the incoming call requests, where themethod includes a schedule filter associated with one of the call listsfor selectively receiving incoming calls based on a geographic locationof the calling devices, end-users, or a date and time, and a dynamicquery engine that generates a verification filter presented to callersassociated with the incoming call requests that do not correspond totelephone numbers on the call list to solicit verified human responsesfrom callers to selectively allow communication access of one or moreincoming call requests to end-user devices, and wherein incoming callrequests corresponding to telephone numbers provided in one of the calllists are immediately terminated and logged in a call log.

In one aspect, the calling devices include a telephonic communicationdevice including a smart phone, a mobile phone, a landline phone, VOIP,or a cell phone.

In one aspect, a schedule filter associated with a geographic locationincludes a geographic range selection that allows end-users to select ageographic range in which to receive incoming call requests that areknown and verified, and that originate within the selected geographicrange, and/or that allows end-users to select a geographic range inwhich to receive incoming calls from designated group or family memberswhen end-users are within the selected geographic range of theend-users' geographic location. Another schedule filter associated witha geographical location allows end-users to block or restrict incomingcalls from various countries, states or cities as well. A country, stateand/or city of origin tab or icon permits end-users to make selectionsamong a list of countries, states, and/or cities provided in a drop downmenu.

In another aspect, a schedule filter associated with a date and timeincludes a date and time selection that allows end-users to select adate and time in which to receive incoming call requests that are knownand verified, and that originate within the date and time selected.

In another aspect, a schedule filter associated with a date and timeincludes a date and time selection that allows end-users to select adate and time in which not to receive incoming call requests that areknown and verified, and that originate within the date and timeselected.

In one aspect, the call lists include a blacklist including telephonenumbers associated with incoming calls that are deemed unwanted andunverified, and a whitelist including telephone numbers associated withincoming calls that are deemed wanted, and verified.

In one aspect, the dynamic query engine includes any of: 1). a questionand answer filter in which callers are asked one or more questions andcallers given answers are compared to correct answers prestored in oneor more look-up tables; 2). a mathematical computation challenge inwhich callers are asked to solve one or more mathematical problems, suchas what is the sum of two numbers; 3) a phrase, sentence, word, numbers,or letters recognition filter in which callers are asked to repeatcertain phrases, sentences, words, numbers or letters when prompted; and4) a caller directive option employed to instruct callers to perform acertain task.

In yet another aspect, the call filter native application includes ahost of pages presented to end-users including a sign-in page, adashboard page, a blacklist page, a whitelist page, a black list overlaypage including operators associated with a contacts page, a call logpage, a message log page, a from input page, a number contains page, anda message contains text page, a group page, a schedule page, a scheduleoverlay page including operators for a schedule filter associated with ageographic location page, and a date and time page.

In one aspect, the geographic location page includes a geographicselector adjustable by end-users for selectively adjusting a geographicrange to receive incoming call requests that originate within theselected geographic range, and/or receive incoming calls from groupand/or family members when end-users are within a selected geographicrange of end-users geographic location.

In another aspect, the dashboard page includes functionalitiesassociated with a blacklist, a whitelist, a call log, a schedule filter,a group, settings, notification, billing, share this application,feedback, help and logout.

In one aspect, the method includes creating a voicemail greeting storedin a voicemail prompt database where incoming call requests areselectively routed to the voicemail greeting upon callers associatedwith incoming call requests correctly providing answers to queriesgenerated from said dynamic engine, upon incoming call requestscorresponding to telephone numbers provided in said whitelist and notassociated with a schedule filter, or upon incoming call requestscorresponding to telephone numbers provided in said whitelist, andsatisfying rules of a created schedule filter.

Introducing a second embodiment of the invention that provides auser-customized call filter system for filtering unwanted calls, saidsystem comprising: a cloud system hosting a user-customized call filterapplication platform stored in a computer-readable memory and executedby one or more processors on one or more servers and including databasesand a dynamic query engine, where the cloud system receives requests,generated by calling devices over a communication network, tocommunicate with end-user devices, where the requests comprise signalsrepresenting telephone numbers associated with the calling devices,where the user-customized call filter application communicates with anative call filter app provided on the end-user devices for comparingtelephone numbers of incoming calls to telephone numbers prestored incall lists to selectively allow the calling devices to communicate withthe end-user devices, where the dynamic query engine generates at leastone verification filter that is presented to callers associated with thecalling devices to solicit a verified human response from the callers toselectively allow communication access of the calling devices to thecalled devices upon receiving a correct response to the verificationfilter, and immediately terminating incoming calls upon receiving anincorrect response to the verification filter.

As yet another example, disclosed is A user-customized call filtersystem for filtering unwanted calls, said system comprising: a cloudsystem hosting a user-customized call filter application platform storedin a computer-readable memory and executed by one or more processors onone or more servers and including databases and a dynamic query engine;

wherein the cloud system receives requests, generated by calling devicesover a communication network, to communicate with end-user devices;

wherein the requests comprise signals representing telephone numbersassociated with the calling devices;

wherein the user-customized call filter application communicates with anative call filter app provided on the end-user devices for comparingtelephone numbers of incoming calls to telephone numbers prestored incall lists to selectively allow the calling devices to communicate withthe end-user devices;

wherein the dynamic query engine generates at least one verificationfilter that is presented to callers associated with the calling devicesto solicit a verified human response from the callers to selectivelyallow communication access of the calling devices to the called devicesupon receiving a correct response to the verification filter, andimmediately terminating incoming calls upon receiving an incorrectresponse to the verification filter;

wherein the system is assembled to be capable of executing a method of:

hosting a user-customized call filter application platform on acloud-based system;

wherein the call filter application software is stored in acomputer-readable memory and executed by one or more processors on oneor more servers communicating with databases;

wherein the cloud system receives incoming call requests, generated bycalling devices over a communication network, to communicate withend-user devices including a call filter native application;

wherein the incoming call requests are associated with telephone numbersgenerated by the calling devices;

wherein end-users customize the call filter native application to createcall lists including prestored telephone numbers that are compared toincoming call requests to filter the incoming call requests;

wherein the method includes a schedule filter associated with one of thecall lists for selectively receiving incoming calls based on ageographic location of the calling devices, based on end-users, or basedon a date and time, and a dynamic query engine that generates averification filter presented to callers associated with the incomingcall requests that do not correspond to telephone numbers on the calllist to solicit verified human responses from callers to selectivelyallow communication access of one or more incoming call requests toend-user devices;

and wherein incoming call requests corresponding to telephone numbersprovided in one of the call lists are immediately terminated and loggedin a call log.

In another aspect, the calling devices include a telephoniccommunication device including a smart phone, a mobile phone, a landlinephone, VOIP, or a cell phone.

In another aspect, a schedule filter associated with a geographiclocation includes a geographic range selection that allows end-users toselect a geographic range in which to receive incoming call requeststhat are known and verified, and that originate within the selectedgeographic range, and/or that allows end-users to select a geographicrange in which to receive incoming calls from designated group or familymembers when end-users are within the selected geographic range of theend-users' geographic location.

In another aspect, another schedule filter associated with ageographical location allows end-users to block or restrict incomingcalls from various countries, states or cities.

In another aspect, a schedule filter associated with a date and timeincludes a date and time selection that allows end-users to select adate and time in which to receive incoming call requests that are knownand verified, and that originate within the date and time selected.

In another aspect, a schedule filter associated with a date and timeincludes a date and time selection that allows end-users to select adate and time in which not to receive incoming call requests that areknown and verified, and that originate within the date and timeselected.

In another aspect, the call lists include a blacklist includingtelephone numbers associated with incoming calls that are deemedunwanted and unverified, and a whitelist including telephone numbersassociated with incoming calls that are deemed wanted, and verified.

These and other objects, features, and advantages of the presentinvention will become more readily apparent from the attached drawingsand the detailed description of the preferred embodiments, which follow.

BRIEF DESCRIPTION OF THE DRAWINGS

The preferred embodiments of the invention will hereinafter be describedin conjunction with the appended drawings provided to illustrate and notto limit the invention, where like designations denote like elements,and in which:

FIG. 1 presents a graphical representation of a user-customized callfiltering system showing caller and end-user electronic devices, such asa mobile phones, in electrical communication with a cloud-based serverhosting a user-customized call filtering platform, via communicationnetworks, for filtering unwanted calls, in accordance with oneembodiment of the present invention;

FIG. 2 presents a screen shot of a sign-in page for accessing theuser-customized call filtering application platform, and native callfilter application provided on end-user devices;

FIG. 3 presents a screen shot of a dashboard listing a host ofoperatives including a blacklist, a whitelist, a call log, a schedule, agroup, settings, notification, billing, sharing of app, feedback, helpand a log out function;

FIG. 4 presents a screen shot of a blacklist page, showing a list oftelephone numbers associated with calling devices deemed unwanted and/orunverified calls and restricted from accessing end-user devices;

FIG. 5 presents a screen shot of a blacklist overlay page, showingvarious functionalities from which users can select telephone numbersand/or text messages from certain callers to store in the blacklistwhere functionalities include contacts, call logs, a message log, aninput number, number contains, and a message contains text;

FIG. 6 presents a screen shot of a contacts page associated with thecontacts functionality of FIG. 5 to permit end-users to select phonenumbers associated with telephone numbers of callers listed in contactsto add to the blacklist to filter such telephone numbers;

FIG. 7 presents a screen shot of a message contain text page, showing alist of text messages previously stored and designated for filtering;

FIG. 8 presents a screen shot of a whitelist, showing a list of callersand phone numbers associated with callers that are deemed known,verified, and given direct access to end-user devices based on created,scheduled filters;

FIGS. 9 and 10 present screen shots of a group page, and create grouppage for creating groups of individuals associated with callingtelephone numbers deemed known, and verified, and given direct access toend-user devices based on created, scheduled filters;

FIGS. 11 and 12 present screen shots of a schedule list page, andschedule list overlay page including schedule filters, respectively,where schedule filters are based on geographic location of incomingcalls, and/or on geographic location of end-users, and a scheduled dateand time for receiving incoming calls;

FIG. 13 presents a screen shot of a schedule by location page associatedwith selecting the geographic location operator in FIG. 12, to customizea geographic range from which originating incoming calls are deemedacceptable and routed to end-users;

FIG. 14 presents a screen shot of a schedule by date and time page uponselecting the date and time operator in FIG. 12 to customize dates,days, and/or times for end-users to receive or prevent from receiving,incoming calls; and

FIG. 15 presents an illustrative flow chart for processing and managingincoming calls based on user-customized schedule filters, and calllists.

Like reference numerals refer to like parts throughout the several viewsof the drawings.

DETAILED DESCRIPTION

The following detailed description is merely exemplary in nature and isnot intended to limit the described embodiments or the application anduses of the described embodiments. As used herein, the word “exemplary”or “illustrative” means “serving as an example, instance, orillustration.” Any implementation described herein as “exemplary” or“illustrative” is not necessarily to be construed as preferred oradvantageous over other implementations. All of the implementationsdescribed below are exemplary implementations provided to enable personsskilled in the art to make or use the embodiments of the disclosure andare not intended to limit the scope of the disclosure, which is definedby the claims. For purposes of description herein, the terms “upper”,“lower”, “left”, “rear”, “right”, “front”, “vertical”, “horizontal”, andderivatives thereof shall relate to the invention as oriented in FIG. 1.Furthermore, there is no intention to be bound by any expressed orimplied theory presented in the preceding technical field, background,brief summary or the following detailed description. It is also to beunderstood that the specific devices and processes illustrated in theattached drawings, and described in the following specification, aresimply exemplary embodiments of the inventive concepts defined in theappended claims. Hence, specific dimensions and other physicalcharacteristics relating to the embodiments disclosed herein are not tobe considered as limiting, unless the claims expressly state otherwise.

Shown throughout the figures, the present invention is directed to auser-customized call filtering system and method for selectivelyfiltering and blocking unwanted or unverified calls based onuser-customized settings including schedule filters associated with awhitelist, and a black list, and includes a dynamic query engine thatgenerates and presents questions to callers associated with incomingcalls to solicit human responses to filter out robocallers. Theuser-customized call filtering system and method comprises a cloud-basedsystem hosting a user-customized call filtering software platform storedin a computer-readable memory and executed by one or more processors,and in communication with a native call filter application provided onend-user devices, over a communication network. End-user navigate a hostof pages provided by the native call filter application to filterunwanted calls. For illustrative purposed only, the term, “end user” asreferred to herein means a called individual, a group of individuals, abusiness entity, establishment or facility, or an individual receivingincoming calls, or associated with an electronic device employed forreceiving incoming calls.

Referring now to FIG. 1, there is shown a graphical representation of auser-customized call filtering system and method (hereafter referred toas UCCF system) in accordance with an embodiment of the presentinvention. The UCCF system and method 100 includes one or moreelectronic devices 102, associated with callers, in electricalcommunication with one or more end-user devices 112 via a cloud-basedsystem 104 hosting a user-customized call filtering software platform(UCCFP), over electrical communication networks 106, 108, and 110.Devices 102, 112 generally comprise handheld mobile or smart phones butmay also comprise tablets, computers, laptops, and landline phonedevices as well. Each device 102, 112 includes all necessary electroniccomponents needed for communicating with the cloud-based system 104, andwith each other. As such, devices 102, 112 include audio and video orelectronic visual display circuitry, input such as a keyboard ortouchpad, memory, one or more processors, I/O interface or API, RAM, ROMprovided for accessing and visually navigating through the hosted UCCFPhosted on one or more cloud-based servers 114. Devices 102, 112 maycomprise thin client hardware for use in service-as-a-systemconfigurations, and client software including any of cloud accessagents, web browsers, graphical user interface, and phone operatingsystems. For exemplary purposes, devices 102 are associated with callingparties or callers, and devices 112 with end-users or called recipients.Thus, devices 102 may represent phones or phone systems or devices usedby any calling party including a person, or machine-operatedrobocallers. All incoming calls initiated by such devices 102 arefiltered before being routed to intended end-user devices 112.

Each electronic communication device 102, 112 is configured tocommunicate with the cloud-based system 104 and server 114 hosting theUCCFP via, a wireless network 106, a wired or landline network 108, or aVOIP (voice over internet protocol) network over the internet 110.Communication networks 106, 108, 110 may include any of, a WLAN(wireless local area network, such as Wi-Fi (IEEE 802.11)), WPANS(wireless personal area networks, such as Bluetooth (IEEE 802.15),Infrared, ZigBee), WMAN (wireless metropolitan area network, such asWiMAX (IEEE 802.16)), WWAN (wireless wide area networks, internet), andGAN (global area network), a telephone network, (e.g., analog, digital,wired, wireless, PSTN (public standard telephone network), ISDN, orXDSL, a mobile wireless communication system, such as 3G, 4G, or newlydeveloped 5G, an internet-protocol based communication system, a radiofrequency network (RF), a cable network, a satellite network, an opticalnetwork, and an internet or intranet network, where each network isadapted for transmitting, and receiving data, information, audio, video,texts, folders, and files between devices 102, 112 and the cloud-basedsystem 104. It is understood that each communication network 106, 108,110 includes all necessary communication or information exchangeequipment, components or peripherals, including, but not limited to, oneor more base stations, one or more servers, routers, switches,repeaters, towers, antennas, Ethernet hubs, wired or wireless datapathways, modems, or gateways to name a few. In one embodiment, datacommunication, or data tunneling occurring between devices 102, 112, andnetworks 106, 108, and 110, may be encrypted using any well-knownencryption process or protocols to secure the transmitted information,data, video, or messages. For example, a few exemplary forms ofencryption include IPsec, or secure sockets layer (SSL), and symmetricor asymmetric encryption.

The cloud-based system 104 includes one or more servers 114 for hostingthe UCCFP software. The one or more servers 114 may be provided on oraccessible by the cloud-based system 104. Each server 114 comprises oneor more computers, I/O and/or network interfaces, processors, memory,and necessary computer readable medium for storing, processing,operating, sharing, transferring, and receiving, data, files, videos,images, audio, and other information, and for performing computations,hosting web pages and/or web applications, maintaining and communicationwith databases, processing software application source code, and otheroperatives associated with the UCCFP software functionalities. In onenon-limiting example, the one or more servers 114 may comprise anapplication server, a web server, a computing server, a communicationsserver, a database/file server, a mail server, a proxy server, or otheradditional servers. The cloud-based server 114 can be managed,controlled and operated by a designated entity, business, internetservice provider, or third party business entity. As such cloud-basedserver 114 may be managed by any of an application service provider(ASP) offering on-demand software or software as a service, a networkservice provider (NSP), an internet service provider (ISP), a managedservice provider (MSP), or a telecommunication service provider (TSP)where providers can charge ongoing subscription or fixed service fees,if any, to users. Server 114 includes memory that may include staticrandom access memory (SRAM), synchronous dynamic RAM (SDRAM),nonvolatile/flash-type memory, or any other type of memory.Machine-executable program instructions or computer application programsassociated with the UCCFP software may be stored on one or more machinereadable mediums, including but not limited to, optical disk, magneticor optical card or tape, flash memory, CD/DVD-ROM, memory dongle,magnetic storage media such as a hard drive or any other externalmachine-readable medium coupled to server or server computer via, I/Ointerface. Computer-accessible medium may include any volatile ornon-volatile media such as RAM (e.g. SDRAM, DDR SDRAM, RDRAM, SRAM,etc.), ROM, EEPROM, or EPROM.

The UCCF system 100 includes a series of databases 116, 118, 120, and122 each hosting, storing, indexing, filing, and managing informationand data associated with filtering unwanted calls from individualsincluding robocallers. Each database 116, 118, 120, 122 is in electricalcommunication with the cloud-based server 114, and includes, or hasaccessible communication or storage capacity with, internal or externalstorage comprising any of floppy or optical disks, CD-ROM, flash memoryor USB storage devices, or other machine readable medium suitable forstoring computer source code, instructions, data tables, look-up tables,files, data, information, or folders. It is appreciated that both theserver(s) 114, and the databases 116, 118, 120, 122 is made part of, isseparately distinct from, the cloud-based system 104. It is alsounderstood that such databases 116, 118, 120 may also be included aspart of each end-user device 112. Thus, databases 116, 118, 120 can beprovided on the cloud-bases system 104 and accessed by end-user devices112, or can be provided in each end-user device 112.

A whitelist database 116 includes a list of electronic identifiers thatare known, and pre-verified for immediate access to end-user devices112. Electronic identifiers include for example, but are not limited to,a mac address, an IP address, a mobile identification number (MIN), aphone number, a software identifier, and a mobile substantiveidentification number (MSIN). For illustrative purposes only, referencemade herein is to electronic identifiers that comprise telephone numbersassociated with calling party devices 102. The whitelist database 116includes a file, folder and/or index manifest, or one or more look-uptables, or any combination thereof. The whitelist database 116 includesan index of prestored or preprogramed telephone numbers associated withcalling party devices 102 owned by friends, family members, or trustedcompanies, third parties, or individuals. Telephone numbers that arestored in the white list database 116 are electronic identifiers deemedautomatically verified by end-users assuring called recipients that suchincoming calls are legitimate and originate from known, verified, andtrusted callers. In practice, telephone numbers of incoming callsassociated with calling party devices 102, are compared to telephonenumbers previously stored within the whitelist database 116 to ascertainwhether the incoming calls are verified or possibly unwanted. Index orlook-up tables may comprise a number of indexes or tables that correlateto, or are associated with, particular attributes relating to friends,groups, family relatives, or businesses, etc. . . .

The UCCF system 100 includes a blacklist database 118 that comprises alist of prestored telephone numbers associated with calling partydevices 102 that are deemed suspicious, non-verified, suspect, spoofedcalls, or unwanted calls that originate from calling devices 102. Inpractice, a host of unwanted telephone numbers are manually orautomatically prestored in the blacklist database 118. Amachine-learning module may be implemented to learn or automaticallyrecognize incoming telephone numbers that are deemed suspect or highlysuspicious and automatically reroute such numbers to a dynamic queryengine 124 for further review of the calling party identity. Theblacklist database 118 further includes a listing of known robocallersmade available by the Federal Trade Commission.

A call management database 120 manages calls, message logs, or activityreports of all incoming calls, including calls that have been terminatedor dropped, been granted access to end-user devices 112, and/or reroutedto the voicemail prompt 122. For example, call logs or activity reportsmay include telephone numbers itemized according to time of day, date,name, geographic location of originating call, names of callers, orother pertinent information and data including a reason as to whyincoming calls were filtered or dropped, type and frequency ofverification or scheduled filters used, and whether callers are on apredesignated list. The call management database 120 may also includeinformation accessible by end-users, and relating to materials foreducating or informing end-users about robocallers, robocalling stateand federal laws, rules, and regulations, methods for preventingrobocallers, and/or to helpful information, solutions, or contactinformation when dealing with robocallers. Such helpful data orinformation may include forms, videos, audio, tutorials, or writtenmaterials relating to robocalling practices and solutions. Otherinformation may teach individuals or walk them through steps on how toseek relief or compensation from known robocallers.

The user-customized call filtering system 100 includes a voicemailgreeting database 122 that includes predefined, and/or user-customized,voice messages, or greetings that are generally presented to unwanted,or unverified callers. The voicemail greeting database 112 may be usedby end-users for a host of reasons. In one example, incoming callsassociated with verified callers are typically granted immediatelyaccess to end-user devices. However, end-users may have programmed theirend-user device 112 to direct or route all incoming calls, or incomingcalls associated to certain callers, to the voicemail greeting database122 to hear personal greetings, a voicemail, or other audibleinstructions, or directives. In another embodiment, incoming calls fromunwanted and unverified callers that are not listed in the whitelistdatabase 116 may be directly routed to the voice greeting database 122.For instance, an incoming call that is known to be a robocaller, or anunverified caller can be directly routed to the voicemail greetingdatabase 122 in an effort to further vet such incoming calls. In yetanother embodiment, incoming calls that have not successfully provided acorrective or proper response to a question generated and presented by adynamic query engine 124 may also be routed directly to the voicemailgreeting database 122. The voicemail greetings database 122 may includemessages like, please do not disturb, we do not accept calls fromunverified callers, or please call Jim, or please provide your contactor identification information, or any other type of voice audiblegenerated greeting that may be affiliated with certain characteristics,profiles, or attributes of end user groups, memberships, interests,profiles, or geographic locations. In one embodiment, end-users mayaccess the UCCFP and via, an authentication process, edit, create,customize, or delete voicemail greetings at any time. In onenon-limiting embodiment, voicemail greetings may be automaticallygenerated based on a known identify of incoming calls. For example, ifan incoming call is from a known, verified caller such as a friend, andthe end-user has selected to activate a voicemail greeting uponreceiving calls from that friend, when the known, verified friend callsin, the person is automatically directed to a voicemail greetinggenerated by the voicemail greeting database 122. The voicemail greetingmay be specifically directed to that particular friend, or may comprisea general greeting intended for all friends. Thus, in one embodiment,users may customize voicemail greetings for particular individuals,groups of individuals, or for unverified, unwanted calls.

A beneficial feature of the UCCF system and method 100 includes adynamic query engine generally denoted at 124 that is used to engage orsolicit communication, in real-time, from callers in an effort toidentify and verify whether such callers are spoofed calls, callsassociated with robocallers, or calls that originate from humans. Thedynamic query engine 124 solicits participation of callers to ascertainattributes from such callers including their identity, reason forcalling, profile, or to ascertain the nature of the call, and whether togive callers access to end-user devices, or to route such incoming callsto the voice greeting database 122 for further vetting. Generally,robocallers comprise electrical machines that are void of human mentalfaculties, capacity or communication. The dynamic query engine 124presents predetermined and stored, or user-customized verification queryfilters designed to solicit human interaction from callers in an effortto verify whether the callers are human, or unwanted, machinerobocallers. Examples of verification query filters include: 1).questions that are presented to unverified callers to solicit answersthat are compared to correct, prestored answers. For example, what dothe initial U.S. represent; 2). a mathematical computation challengethat are presented to unverified callers to solve where mathematicalanswers are compared to correct, prestored answers. For example what isthe sum of three and three; 3) provide a phrase(s), sentence(s),word(s), number(s), or letter(s) to callers and ask such callers torecite or repeat the phrase(s), sentence(s), word(s), number(s) orletter(s) when prompted; and/or 4) provide calls a directive thatinstruct callers to perform a certain task. For example, a directiveoption may include, if you are Mr. Smith please press one, or if you arenot Chuck, please press three. Another directive option may instructcallers to enter a specific combination or sequence of keys that arerandomly generated by the dynamic query engine, or customized by usersto solicit the caller's entry of instructed sequence of keys. Forinstance, callers may be prompted to enter a sequence of keys such asone, four, and eight. The dynamic query engine 124 randomly generatesthe verification filters presented to callers. For example, amathematical computation challenge can be changed every minute, hours,or day, with new mathematical challenges, a question and answer sessionmay follow a caller direction option, or a phrase recognition filter maybe used three consecutive times in one hour, followed by a sequentialkey entry instruction. As such, presenting different verificationfilters to callers makes it difficult for robocallers to adopt amachine-learning approach in recognizing or learning types, times, orchanges of verification filters presented. Callers who respond correctlyto verification filters are deemed verified humans and may be granted,upon selection from end-users, access to end-user devices 112. Ifcallers do not respond to such verification filters correctly, suchcalls are immediately disconnected, or routed to the voicemail prompt122 and denied immediate access to end-user devices.

A user identification and authentication module 126 is employed toauthenticate the identity of callers and determine whether the caller isa person who is authorized to use the device 102, or is the true ownerof the calling device 102. To address this concern, system 100 requirescallers to authenticate the use of the device 102 itself, andauthenticate accessibility to the UCCF software platform. Theauthentication module 126 includes authentication protocols such as, butnot limited to, a single-tier, two-tier, or multi-tier authenticationprotocol process, tokens, digital certificates, or biometricauthentication using one or more sensors embedded within, or providedseparately for use with, calling devices 102. Such embedded sensors maysense fingerprints, hand geometry, iris or retinal patterns, facialfeatures, hand gestures, or voice sampling or recognition. Onewell-known form of authentication protocol comprises a two-tier systemoften including username and password. User device authentication mayoccur at the device 102 itself where the device 102 includes built-inlogin technology and authentication components to verify that callersare calling from a mobile phone which utilizes authenticationtechnology, or alternatively, authentication may occur on thecloud-based system 104 that hosts authentication software where theelectronic device 102 transmits authentication information to the UCCFSplatform to authenticate the information transmitted from the device102. For example, a caller may use a mobile phone to take a picture ofthe person's face, or a fingerprint sensor to scan fingerprints, wherethe photo or fingerprints are then uploaded onto the cloud-based system104 for authentication. The UCCF platform communicates with the device102 to verify the caller's identity and is not a robocaller.

The UCCF system and method 100 further includes a phone-to-phoneverification module 128 for identifying calling devices 102 to also helpdetermine whether incoming calls are associated with robocallers. Forexample, in one non-limiting embodiment, the phone-to-phone verificationmodule 128 is configured to receive any of a caller's Mac address, aunique IMEI number identifying the make, model and serial number of thecalling device 102, an International Mobile Subscriber Identity (IMSI)number which is the international standardized unique number to identifya mobile subscriber, or an IP address associated with VOIP calls thatare made over the internet 110. The received numbers or addresses areanalyzed to confirm that callers are not using spoofed numbers.

A pinged or trace signal generator 130 is employed to help identifyincoming calls by automatically generating a return call, orautomatically transmitting a pinged signal to calling devices 102 to mapor trace incoming calls to determine if the calling party is actuallycalling from the device 102 identified, and/or to determine thegeographic location of the device 102. For example, the signal generator130 may send an SMS, an email, or a voice prompt to solicit a pinglocation response. The SMS text may include a code reviewable by callingparties to enter into a validation prompt to verify and validateidentity of the calling party.

In one embodiment, end-users may access a designated website via, auniversal resource code locator (URL) to download a native call filterapplication (NCF APP) onto end-user devices 112. The NCF APP includes aseries of program interfaces API that allow users to navigate andcommunicate with the UCCF software platform that is hosted on thecloud-based system 104. For example, one or more program interfacescreens are navigated by users to view, edit, insert, amend, navigate,print, set-up, delete, register, transmit, or store, any data, files,folders, pictures, telephone numbers, videos, audio, forms, profiles,verification filters, or any information, input or data relating to theNCF APP and/or UCCF software platform. The one or more interfaces mayemploy any of, toggle buttons, drop-down menus, tabs, task-based icons,menus, query boxes, collapsible bars or banners, dashboards, tools, orother web-based interfacing, that is organized, structured, formatted,or developed for accessible use by subscribed users, or allowed users.The API can be engineered and designed to include a specific layout ofoperative features that are presented to users in a particular format ormanner.

Upon launching the NCF APP, end-users are presented a screen shot of asign-in page 200 to begin the process of filtering incoming calls and/ortexts, and to access the user-customized call filtering softwareplatform hosted on the cloud-bases system 104. The sign-in page 200includes, in one non-limiting embodiment, a two-tier authenticationprotocol that uses sign-in credentials attributed to an end-user's emailaddress or mobile phone number 202 in one tier, and a password 204 inanother tier. End-users may sign-in through social media including forexample, Facebook®, Twitter®, or Google Play®, illustrated at 206.Non-registered users may also sign up for the first time if they havenot already established an account. Such sign-in credentials maycomprise other forms including for example, use of CAPTCHA,bio-authentication, tokens, digital certificates, or use of electronicidentifiers associated with end-user device 112. The authenticationprotocol may include any format including for example, passwordauthentication protocol (PAP), challenge-handshake authenticationprotocol (CHAP), or extensible authentication protocol (EAP). Type ofservices provided may be based on an authenticated hierarchy basis. Forexample, amount of services rendered or accessible may be cost drivenwhere more services made available for use by end-users is proportionalto service fees. Thus, authentication protocols may be associated withthe types of services paid for, the service fee paid, or any combinationthereof.

Upon authenticated access to the NCF APP, authorized end-users aredirected to a screen shot of a dashboard page 300 that includes aplurality of operators or functionalities denoted at 302 for effectivelyfiltering or blocking unwanted and/or unverified incoming calls. Theplurality of operators 302 includes, in one non-limiting example, ablacklist, a whitelist, a call log, a schedule, a group, settings,notification, billing, sharing of app, feedback, help and a log outfunction. The dashboard page 300 also includes profile informationassociated with the end-user 304. Such profile information may beprovided upon registering as a first time user and can be edited anytimevia, and edit profile icon 306.

End-users navigate through the list of operatives 302 provided on thedashboard page 300 to interact with the NCF APP to effectively block orfilter unwanted or unverified calls that are initiated from callerdevices 102, as shown in FIG. 1. In do so, end-users generally begincustomizing the call filtering process by generating a blacklist via, ablacklist page 400 illustrated in FIG. 4. The blacklist is tailored tofilter or block unwanted or unverified phone numbers of callersassociated with known and unwanted, or unknown individuals, parties, orentities, including robocallers from gaining access to end-user devices112 including smart phones. The blacklist page 400 allows users toselectively filter or block unwanted and/or unverified phone calls byactivating a toggle call button 402, or filter and block unwanted and/orunverified texts by activating a toggle SMS button 404. A list ofpre-customized and prestored phone numbers is generated in alphabeticalorder for added convenience. The blacklist page 400 allows end-users toadd any phone number that is associated with unwanted or unverifiedcallers including robocallers via, a caller add icon 409. The blacklistmay also include, or have access to a database that includes, a robocallindex including a list of phone numbers that are known robocallers thatis provided by the Federal Trade Commission.

Upon activating the add icon 409 (represented as a plus symbol),end-users are provided with an overlay page 410 as illustrated in FIG.5. The overlay page 410 allows end-users to populate the blacklist withphone numbers and/or text messages associated with known, unwanted, orunverified callers using various modalities including in onenon-limiting example, contacts 412, a call log 414, a message log 416,and/or from a list of input numbers 418. Choosing the modalityidentified as contacts 412 on the overlay page 410, directs end-users toa contact list page 500, illustrated in FIG. 6. The contact list page500 generally includes a plurality of phone numbers that are associatedwith individual friends, family, or other known callers. As shown inFIG. 6, the contact list includes individual names that are eachassociated with a phone number as depicted for illustrative purposes at502, 504, and 506. End-users populate or customize the blacklist byselecting individuals from the contact list. End-users may restrict,filter or block any calls emanating from such selected individuals bysimply checking the box that corresponds to each person as shown at 508and 510. Once selection is made, end-users activate the accept icon asrepresented by mark 512. Upon adding the selected individuals, the phonenumbers associated with selected individuals 504, 506 will beautomatically stored in the blacklist to block calls, originating fromthe selected individuals 504, 506, from gaining access to end-userdevices 112. End-users may access the contacts functionality 412 to addor remove phone numbers at any time.

End-users may also filter or block phone numbers and/or text messages ofincoming calls and/or texts, based on call logs, 414, a message log 416,from an input number 418, a number contains 420, and/or a text messageor part of a text message contains 422 functionality. In oneillustrative example, upon selecting, the number contains 420functionality, end-users may enter a sequence of numbers that aresusceptible, considered, or known to correspond to an unwanted orunverified caller. For instance, if a phone number associated with anunwanted call or robocaller includes particular numbers or digits thatcorrespond to an area code, end-users may enter the sequence of numbersin the number contains 420 data insert box where all incoming callshaving an area code that matches with the prestored sequence of numbersare automatically dropped, and routed to the voicemail prompt 122, orare routed to the dynamic query engine for further vetting.

When selecting the message contains text 422 functionality presented inoverlay page 410, end-users are directed to a message contains text page600, as illustrated in FIG. 7. A data input box 602 is presented forend-users to enter text words associated with unwanted text messages, orvoicemail messages. Thus, end-users customize the blacklist page 400 tofilter or block incoming text messages that contain words or phrasesentered in the data input box 602, and readily prestored in theblacklist by end-users. Any number of text messages are prestored, asillustrated at 604 in FIG. 7 using add icon 606. It is understood thateach prestored text message 604 may include a corresponding box thatallows end-users to select or deselect which text message 604 to block,similar to checked boxes 508, 510 shown in FIG. 6. It is understood thatthe blacklist may be populated with information, data, phone numbers, ortext messages that are provided in emails, calendars, memos, or socialmedia forums. Thus, overlay page 410 may include additional operators orfunctionalities that allow prestoring information from emails,calendars, memo, and from social media where selecting such a socialmedia operator may direct end-users to a social media overlay page thatincludes social media operators including those provided at 206 in FIG.2.

Turning to FIGS. 3 and 8, the NCF APP also provides a whitelistoperative to provide a whitelist page denoted at 700 in FIG. 8. Thewhitelist page 700 includes a list of phone numbers prestored byend-users, and associated with calling devices owned or used by known,trusted, and/or verified callers 702 including for example, closefriends, family members, doctors office, affiliated group members, orwork related colleagues. Incoming calls including phone numbers listedon the whitelist are either immediately directed to end-user devices112, or are routed to a voicemail prompt 122 in the event calls fromsuch callers are tagged with a schedule filter setting. Any number ofphone numbers and/or text messages are added in the whitelist via, addicon 704.

As shown at the bottom of the page 700 in FIG. 8, a group icon or tab800 directs end-users to a group page denoted at 900 in FIG. 12. Grouppage 900 includes previously created groups of individuals characterizedas a home group 902, and a family group 904. Each group 902, 904includes one or more phone numbers of known or verified individuals. Anynumber of groups may be added via, a group add icon 906. Upon selectingthe group add icon 906, end-users are directed to a create group page908 where end-users can customize the names, and profile information ofeach group member. For instance, phone numbers of individual familymembers can be stored in a group 904 characterized as family. Otherexemplary forms of group identification may include religious groups,political party groups, groups affiliated with the rotary club, orchamber of commerce, includes individuals involved in sports or teams,or members of various clubs to name a few. Multiple groups are easilycreated by activating the group create icon 910 shown in FIG. 10.

The whitelist highlighted in the whitelist page 700 is governed by a setof rules that define schedule filter settings that allow end-users tocustomize when they wish to receive calls and/or from what geographicallocation calls originate, as illustrated in FIGS. 11-14. The schedulefilter setting provides a schedule page 1000 that includes a scheduletoggle button 1002 which activates schedule filters for receiving callsfrom individuals listed according to created groups shown in oneembodiment as a family group 1004, and a home group 1006 where eachgroup includes phone numbers of known, verified individual callersprestored in the whitelist. As shown in FIG. 11, each group 1004, 1006includes a corresponding schedule toggle button 1008, 1010,respectively, to selectively apply a schedule filter to one or morephone numbers associated with incoming calls. Upon activating scheduletoggle button 1002, and 1008, end-users are directed to an overlayschedule page 1012 that gives end-users the ability to set a schedulefilter for incoming calls based on geographic location via, locationicon 1014, and on one or more dates and times via, date and time icon1016.

Upon selecting location icon 1014, end-users are directed to a scheduleby location page 2000 shown in FIG. 10. The schedule by location page2000 includes a header 2002 that identifies the prestored groupconsidered for setting-up a schedule filter. In one embodiment, adrop-down can be included to allow end-users to view and individuallyselect phone numbers associated with individuals that are listed in thegroup represented. A map 2004 of the geographical region associated withthe location of the end-user is provided on the screen display of theend user's electronic device 112. A geographical location marker 2006,associated with a global positioning system (GPS) embedded in end-userelectronic devices 112, indicates the current geographical location ofend-users while physically located within the geographical region. Ageographical range selector 2008 allows end-users to customize thegeographical distance between callers and end-users for filteringincoming calls based on the location of the originating caller, and/orthe geographic location of the end-user. Thus, incoming calls fromknown, verified callers that originate outside the geographical range ordistance selected are filtered by routing such calls to the voicemailprompt 122 for review later. For instance, as illustrated in FIG. 13,end-users may customize a filtered geographical range of 2 miles whereincoming calls from known, verified callers that originate within a 2mile radius of the end-user's geographical position, (represented by acircular gray zone in FIG. 13) are granted immediate access to end-userdevices 112 where incoming calls that originate from outside the 2 mileradius are filtered or blocked and routed to the voicemail prompt 122.The geographical range selector 2008 is adjustable to increase ordecrease the geographical range of filtering. Upon customizing thegeographical range filter, end-users save the information via, an addicon 2010. Although the geographical range selector 2008 is shown as asliding operator, such selector 2008 may comprise one or more rotatingwheels, or a check-box selection of predefined ranges. It is understoodin one embodiment, end-users can customize geographical ranges orlocations for individual callers, and/or groups of callers. All incomingcalls that are unknown and/or unverified and that originate from anygeographical location, whether inside or outside of the customizedgeographical range, are either immediately dropped as a result of beinglisted on the blacklist, or routed to the dynamic query engine 124 forfurther vetting. Further, end-users can select a geographic range inwhich to receive incoming calls based on the geographic location of theend-user. For instance, an end-user may be at home and desires toreceive incoming calls from members of a designated group or family,that were created via, the group page 908, when the end-user in within acertain geographic range from the home. Thus, if an end-user selects ageographic range of say 10 miles, via range selector 2008, and theend-user is physically at a residence, then the end-user will receiveincoming calls from members of the group or family when the end-user isphysically located within 10 miles of the residence. Coordinatesprovided by the global positioning system (GPS) embedded in end-userelectronic devices, i.e. smart phones, provides the geographic referenceto determine the present location of the end-user at all times. If theend-user is physically located outside the selected 10-mile range, theincoming calls are routed to the voice prompt/greeting 122. It is notedthat a geographic algorithm may be implemented to determine and processcorrelation of geographic ranges selected and physical geographiclocation of end-users.

In one embodiment, there is also provided another schedule filter basedon country of origin, states, and/or cities. End-users may block orprevent receiving incoming calls that originate from certain countries,states and/or cities. A drop down menu listing a host of countries,states and/or cities is made available to end-users via the NCF APP, toallow end-users to easily and quickly select what countries, statesand/or cities they wish to block originating calls from. Callsoriginating from other countries, states and/or cities generally includedifferent area country, state or city codes provided in the telephonenumber associated with the incoming call. Such country, state and/orcity codes may be processed to determine their origin and whether suchorigins were selected as blocked by end-users. Incoming calls deemed tobe from a blocked country, state or city, is routed to the voice prompt122, or to the dynamic query engine 124.

A date and time schedule filter allows end-users to schedule incomingcalls, previously stored on the whitelist, based on dates, or days of aweek, and times. Upon selecting the date and time icon 1016 shown onschedule overlay page 1012 of FIG. 12, end-users are directed to aschedule by date and time page 3000 illustrated in FIG. 14. The scheduledate and time page 3000 includes a header 3002 identifying a previouslycreated group, or individuals in the group, considered for setting-up adate and time schedule filter. In one embodiment, a drop-down operatormay allow end-users to view and individually select phone numbersassociated with known, verified individuals that were prestored earlier.End-users can customize receiving incoming calls from known, verifiedcallers in accordance with a start date 3004, and an end date 3006, anda start time 3008, and an end time 3010. Thus, in one example, end-usersmay select a start date of Jun. 1, 2020, and an end date of Jun. 7,2020, with a start time of 3 pm and end time of 11 pm for each daterange. A calendar system is presented to users upon activating the startand end date icons 3004, 3006, and a time system illustrated as hour andminute is presented to users upon activating the start and end timeicons 3008, and 3010. End-users can also block receiving calls based onparticular days of the week as illustrated at 3012, 3014, and 3016. Forexample, end-users may wish to block calls on Monday 3012, Thursday3014, and Saturday 3016 by checking the corresponding box associatedwith each day of the week. For instance, an end-user may wish to blockcalls on Monday 3012 from 3 pm to 5 pm. The ability to block incomingcalls based on dates, days of the weeks, and times provides a convenienttool for end-users that wish not be bothered by calls for variousreasons including for example, while at the doctor's office, whileattending a religious ceremony, while driving on route, or during abusiness meeting. Incoming calls that occur outside prescheduled dates,days, and times are routed to the voicemail prompt 122. Incoming callslisted on the blacklist are immediately dropped, and incoming calls fromunknown and unverified individuals are routed to the dynamic queryengine 124 for further vetting.

A non-limiting process or method of filtering incoming calls and/ortexts directed at end-user devices 112 is illustrated in FIG. 15. Theprocess or method is operatively illustrated in reference to a singleincoming call and/or text, however, it is generally understood theprocess and method functions for all incoming calls and/or texts. Asdemonstrated in step 4000, an incoming call and/or text is processed todetermine whether the incoming call or text is one that waspreprogrammed or prestored on an end-user customized whitelist. If theincoming call or text is listed on a customized whitelist, determinationis made as to whether the end-user has created and associated a schedulefiler attributed to the incoming call as illustrated in step 4002. Ascheduled filter may include filtering incoming known, or verified callsbased on geographic location of originating incoming call, or on date,day of the week, and time. If an end-user has not created a scheduledfilter for the incoming call or text, the incoming call and/or text isforwarded and granted access to the calling end-user device 112, asshown in step 4004. However, if the end-user has generated a scheduledfilter per the steps outlined in FIGS. 11-14, the incoming call and ortext is processed in accordance with the customized generated schedulefilter, and routed to the voicemail prompt 122, logged in a call log,and the end-user is notified of the call or text, as provided in step4006.

As demonstrated in step 4008, an incoming call and/or text is processedto determine whether the incoming call or text is one that waspreprogrammed or prestored on an end-user customized blacklist. If theincoming call or text is listed on a customized blacklist, the incomingcall is immediately dropped, and recorded in a call log, as provided instep 4010. However, if the incoming call is not listed on a whitelist,and is not listed on a black list, the incoming call is routed to thedynamic query engine 124, where one or more queries are presented to thecaller to solicit a correct, human response in order to ascertainwhether the caller is human, or comprises a possible robocaller, asshown in step 4012. If the caller, associated with the incoming call,provides correct responses to one or more queries represented to thecaller, as shown in step 4014, a determination is made that the calleris human, and the call is forwarded to the end-user at step 4004.Determining whether the incoming calls is made from a human may, in oneembodiment, entail consideration as to how many solicited answers arecorrect, the length of time it takes to answer one or more questions,analyzing the audible tone of the response, the type of answer given bythe caller, and other possible factors. If the caller, associated withthe incoming call, provides an incorrect response to a predeterminednumber of questions, the incoming call is directed or routed to thevoicemail prompt 122, the call is logged in the call log, and notice isprovided to the end-user called recipient.

All incoming calls are listed in a call log and available for review toascertain what incoming calls, if any, are associated with robocallersor spoofed calls. Each incoming call stored in the call log is stampedwith a date and time the calls were initiated. Calls determined to havebeen made from robocallers may be manually selected via, 414 in FIG. 5,or automatically stored on the blacklist page 400. A machine-learningmodule may be employed to learn the frequency, pattern, originatinglocation of, length of rings, identification of calling number, toascertain whether incoming calls are ones made from robocallers. Themachine-learning module may automatically place the incoming call in theblacklist.

Returning to FIG. 3, dashboard page 300 includes additional operatorsidentified for example as settings, notification, billing, share thisapp, feedback, help and log out. The settings operator allows end-usersto edit or create profile and account information, and the notificationoperator allows end-users to set-up notifications after certain eventshave occurred such as when incoming calls are routed to the voicemailprompt 122. End-users may customize the manner in which notificationsare made including being able to select a visual indicator via, email ortext, a visual symbol or character, or an audible indicator comprisingmusic, a single ring, a buzzer, a charm or other sounding format.End-users can share the NCF APP with others via the share operator, andcan make payments for services provided via, the billing operator.End-users can provide feedback to help improve or comment on, the NCFAPP, and can initiate the help tab to access written, audible or videoformats of information to assist end-users in using and navigating theNCF APP. Finally, end-users can safely log-out of the system via, thelog-out operator. It is understood dashboard page 300 may includeadditional operators associated with other functionalities to furtheraccommodate end-users. For instance, a language selector operator mayallow users to interact with the NCF APP in a preferred language such asEnglish, French, Japanese, may include a filter that allows receivingincoming calls from individuals subscribed to the same cell phoneservice as end-users, and may include options for end-users to customizehow or where to route unwanted calls.

The user-customized call filtering system and method 100 is designed tosupport a plug-in architecture that includes add-ons, extensions, fileor folder extensions or manifests, software code, or components foradding, removing, and/or changing, user-specific functionalities, and toaddress the need for software updates, modifications, or other changesthat may be required from time to time.

Since many modifications, variations, and changes in detail can be madeto the described preferred embodiments of the invention, it is intendedthat all matters in the foregoing description and shown in theaccompanying drawings be interpreted as illustrative and not aslimiting. Furthermore, it is understood that any of the featurespresented in the embodiments may be integrated into any otherembodiments unless explicitly stated otherwise.

What is claimed is:
 1. A user-customized method of filtering calls, saidmethod comprising: hosting a user-customized call filter applicationplatform on a cloud-based system; wherein the call filter applicationsoftware is stored in a computer-readable memory and executed by one ormore processors on one or more servers communicating with databases;wherein the cloud system receives incoming call requests, generated bycalling devices over a communication network, to communicate withend-user devices including a call filter native application; wherein theincoming call requests are associated with telephone numbers generatedby the calling devices; wherein end-users customize the call filternative application to create call lists including prestored telephonenumbers that are compared to incoming call requests to filter theincoming call requests; wherein the method includes a schedule filterassociated with one of the call lists for selectively receiving incomingcalls based on a geographic location of the calling devices, based onend-users, or based on a date and time, and a dynamic query engine thatgenerates a verification filter presented to callers associated with theincoming call requests that do not correspond to telephone numbers onthe call list to solicit verified human responses from callers toselectively allow communication access of one or more incoming callrequests to end-user devices; and wherein incoming call requestscorresponding to telephone numbers provided in one of the call lists areimmediately terminated and logged in a call log.
 2. The method of claim1, wherein the calling devices include a telephonic communication deviceincluding a smart phone, a mobile phone, a landline phone, VOIP, or acell phone.
 3. The method of claim 1, wherein a schedule filterassociated with a geographic location includes a geographic rangeselection that allows end-users to select a geographic range in which toreceive incoming call requests that are known and verified, and thatoriginate within the selected geographic range, and/or that allowsend-users to select a geographic range in which to receive incomingcalls from designated group or family members when end-users are withinthe selected geographic range of the end-users' geographic location. 4.The method of claim 3, wherein another schedule filter associated with ageographical location allows end-users to block or restrict incomingcalls from various countries, states or cities.
 5. The method of claim1, wherein a schedule filter associated with a date and time includes adate and time selection that allows end-users to select a date and timein which to receive incoming call requests that are known and verified,and that originate within the date and time selected.
 6. The method ofclaim 1, wherein a schedule filter associated with a date and timeincludes a date and time selection that allows end-users to select adate and time in which not to receive incoming call requests that areknown and verified, and that originate within the date and timeselected.
 7. The method of claim 1, wherein the call lists include ablacklist including telephone numbers associated with incoming callsthat are deemed unwanted and unverified, and a whitelist includingtelephone numbers associated with incoming calls that are deemed wanted,and verified.
 8. The method of claim 1, wherein the dynamic query engineincludes any of: 1) a question and answer filter in which callers areasked one or more questions and callers given answers are compared tocorrect answers prestored in one or more look-up tables; 2) amathematical computation challenge in which callers are asked to solveone or more mathematical problems; 3) a phrase, sentence, word, numbers,or letters recognition filter in which callers are asked to repeatcertain phrases, sentences, words, numbers or letters when prompted; and4) a caller directive option employed to instruct callers to perform acertain task.
 9. The method of claim 1, wherein the call filter nativeapplication includes a host of pages presented to end-users including asign-in page, a dashboard page, a blacklist page, a whitelist page, ablack list overlay page including operators associated with a contactspage, a call log page, a message log page, a from input page, a numbercontains page, and a message contains text page, a group page, aschedule page, a schedule overlay page including operators for aschedule filter associated with a geographic location page, and a dateand time page.
 10. The method of claim 1, wherein the geographiclocation page includes a geographic selector adjustable by end-users forselectively adjusting a geographic range to receive incoming callrequests that originate within the selected geographic range, and/orreceive incoming calls from group and/or family members when end-usersare within a selected geographic range of end-users geographic location.11. The method of claim 1, wherein the dashboard page includesfunctionalities associated with a blacklist, a whitelist, a call log, aschedule filter, a group, settings, notification, billing, share thisapplication, feedback, help and logout.
 12. The method of claim 1,wherein the method includes creating a voicemail greeting stored in avoicemail prompt database where incoming call requests are selectivelyrouted to the voicemail greeting upon callers associated with incomingcall requests correctly providing answers to queries generated from saiddynamic engine, upon incoming call requests corresponding to telephonenumbers provided in said whitelist and not associated with a schedulefilter, or upon incoming call requests corresponding to telephonenumbers provided in said whitelist, and satisfying rules of a createdschedule filter.
 13. A user-customized call filter system for filteringunwanted calls, said system comprising: a cloud system hosting auser-customized call filter application platform stored in acomputer-readable memory and executed by one or more processors on oneor more servers and including databases and a dynamic query engine;wherein the cloud system receives requests, generated by calling devicesover a communication network, to communicate with end-user devices;wherein the requests comprise signals representing telephone numbersassociated with the calling devices; wherein the user-customized callfilter application communicates with a native call filter app providedon the end-user devices for comparing telephone numbers of incomingcalls to telephone numbers prestored in call lists to selectively allowthe calling devices to communicate with the end-user devices; whereinthe dynamic query engine generates at least one verification filter thatis presented to callers associated with the calling devices to solicit averified human response from the callers to selectively allowcommunication access of the calling devices to the called devices uponreceiving a correct response to the verification filter, and immediatelyterminating incoming calls upon receiving an incorrect response to theverification filter.
 14. A user-customized call filter system forfiltering unwanted calls, said system comprising: a cloud system hostinga user-customized call filter application platform stored in acomputer-readable memory and executed by one or more processors on oneor more servers and including databases and a dynamic query engine;wherein the cloud system receives requests, generated by calling devicesover a communication network, to communicate with end-user devices;wherein the requests comprise signals representing telephone numbersassociated with the calling devices; wherein the user-customized callfilter application communicates with a native call filter app providedon the end-user devices for comparing telephone numbers of incomingcalls to telephone numbers prestored in call lists to selectively allowthe calling devices to communicate with the end-user devices; whereinthe dynamic query engine generates at least one verification filter thatis presented to callers associated with the calling devices to solicit averified human response from the callers to selectively allowcommunication access of the calling devices to the called devices uponreceiving a correct response to the verification filter, and immediatelyterminating incoming calls upon receiving an incorrect response to theverification filter; wherein the system is assembled to be capable ofexecuting a method of: hosting a user-customized call filter applicationplatform on a cloud-based system; wherein the call filter applicationsoftware is stored in a computer-readable memory and executed by one ormore processors on one or more servers communicating with databases;wherein the cloud system receives incoming call requests, generated bycalling devices over a communication network, to communicate withend-user devices including a call filter native application; wherein theincoming call requests are associated with telephone numbers generatedby the calling devices; wherein end-users customize the call filternative application to create call lists including prestored telephonenumbers that are compared to incoming call requests to filter theincoming call requests; wherein the method includes a schedule filterassociated with one of the call lists for selectively receiving incomingcalls based on a geographic location of the calling devices, based onend-users, or based on a date and time, and a dynamic query engine thatgenerates a verification filter presented to callers associated with theincoming call requests that do not correspond to telephone numbers onthe call list to solicit verified human responses from callers toselectively allow communication access of one or more incoming callrequests to end-user devices; and wherein incoming call requestscorresponding to telephone numbers provided in one of the call lists areimmediately terminated and logged in a call log.
 15. The method of claim14, wherein the calling devices include a telephonic communicationdevice including a smart phone, a mobile phone, a landline phone, VOIP,or a cell phone.
 16. The method of claim 14, wherein a schedule filterassociated with a geographic location includes a geographic rangeselection that allows end-users to select a geographic range in which toreceive incoming call requests that are known and verified, and thatoriginate within the selected geographic range, and/or that allowsend-users to select a geographic range in which to receive incomingcalls from designated group or family members when end-users are withinthe selected geographic range of the end-users' geographic location. 17.The method of claim 16, wherein another schedule filter associated witha geographical location allows end-users to block or restrict incomingcalls from various countries, states or cities.
 18. The method of claim14, wherein a schedule filter associated with a date and time includes adate and time selection that allows end-users to select a date and timein which to receive incoming call requests that are known and verified,and that originate within the date and time selected.
 19. The method ofclaim 14, wherein a schedule filter associated with a date and timeincludes a date and time selection that allows end-users to select adate and time in which not to receive incoming call requests that areknown and verified, and that originate within the date and timeselected.
 20. The method of claim 14, wherein the call lists include ablacklist including telephone numbers associated with incoming callsthat are deemed unwanted and unverified, and a whitelist includingtelephone numbers associated with incoming calls that are deemed wanted,and verified.